Pin pypa/gh-action-pypi-publish to v1.14.0 by commit SHA#49
Merged
Conversation
The previous reference `pypa/gh-action-pypi-publish@v1.14` does not
resolve — the action only ships full `vX.Y.Z` tags, not abbreviated
`vX.Y` ones. This broke the publish workflow on the v1.7.2 release
("Unable to resolve action ... unable to find version `v1.14`").
Pin to the v1.14.0 commit SHA rather than the floating tag so an
upstream tag move can't silently swap the action under us (the
publish job has `id-token: write` and uploads to PyPI).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The previous reference
pypa/gh-action-pypi-publish@v1.14does not resolve — the action only ships fullvX.Y.Ztags, not abbreviatedvX.Yones. This broke the publish workflow on the v1.7.2 release ("Unable to resolve action ... unable to find versionv1.14").Pin to the v1.14.0 commit SHA rather than the floating tag so an upstream tag move can't silently swap the action under us (the publish job has
id-token: writeand uploads to PyPI).